Skip to main content
TrustRadius
CircleCI

CircleCI

Starting at $0 per month
View Pricing

Overview

What is CircleCI?

CircleCI is a software delivery engine from the company of the same name in San Francisco, that helps teams ship software faster, offering their platform for Continuous Integration and Continuous Delivery (CI/CD). Ultimately, the solution helps to map every source…

Read more
Recent Reviews

TrustRadius Insights

CircleCI is a widely used continuous integration and deployment tool that helps engineering teams streamline their application development …
Continue reading

CircleCI Review

7 out of 10
February 03, 2020
Incentivized
We use CircleCI as an independent part of our continuous integration testing process, which handles both automated building and testing …
Continue reading

CircleCI is awesome

9 out of 10
December 10, 2018
Incentivized
We're using CircleCI to run continuous integration for both front-end and back-end components for a SaaS application. It's linked to a …
Continue reading

Automation done right

8 out of 10
April 30, 2018
Incentivized
In our company, we develop our financial product atop the Salesforce platform. We have extensive unit test coverage that is required by …
Continue reading
Read all reviews

Reviewer Pros & Cons

View all pros & cons
Return to navigation

Pricing

View all pricing

Free

$0

Cloud
per month

Performance

$30

Cloud
per month

Server

$35

Cloud
per month

Entry-level set up fee?

  • No setup fee

Offerings

  • Free Trial
  • Free/Freemium Version
  • Premium Consulting/Integration Services
Return to navigation

Product Demos

CircleCI Demo Series - Deploy your project to AWS ECS

YouTube

How to Build, Test, and Deploy React Native Projects on CircleCI

YouTube

CircleCI Webhooks Demo | How to Get Started

YouTube

CircleCI Scheduled Pipelines | Getting Started

YouTube

Demo | Server Install of CircleCI 2.16 on AWS with Terraform

YouTube

CircleCI Demo

YouTube
Return to navigation

Product Details

What is CircleCI?

CircleCI is a shared continuous integration and continuous delivery (CI/CD) platform, and the central hub where code moves from idea to delivery. It is a DevOps tool that processes more than 1 million builds a day, and has access to data on how engineering teams work, and how their code runs. CircleCI boasts companies like Spotify, Coinbase, Stitch Fix, and BuzzFeed as users.

CircleCI Video

CircleCI Overview

CircleCI Competitors

CircleCI Technical Details

Deployment TypesOn-premise, Software as a Service (SaaS), Cloud, or Web-Based
Operating SystemsWindows, Linux, Mac, Docker
Mobile ApplicationApple iOS, Android
Supported LanguagesEnglish, Japanese

Frequently Asked Questions

CircleCI is a software delivery engine from the company of the same name in San Francisco, that helps teams ship software faster, offering their platform for Continuous Integration and Continuous Delivery (CI/CD). Ultimately, the solution helps to map every source of change for software teams, so they can accelerate innovation and growth.

GitHub, Jenkins, and GitLab are common alternatives for CircleCI.

Reviewers rate Performance highest, with a score of 7.8.

The most common users of CircleCI are from Small Businesses (1-50 employees).
Return to navigation

Comparisons

View all alternatives
Return to navigation

Reviews and Ratings

(49)

Community Insights

TrustRadius Insights are summaries of user sentiment data from TrustRadius reviews and, when necessary, 3rd-party data sources. Have feedback on this content? Let us know!

CircleCI is a widely used continuous integration and deployment tool that helps engineering teams streamline their application development workflows. By integrating tightly with GitHub, CircleCI allows for easy integration into pull request checks, ensuring that tests and linters are automatically run for every pull request and merge. Users have praised CircleCI for its reliability and responsiveness, noting that it has fewer problems compared to other CI tools they have used in the past. The support provided by CircleCI is also highly regarded, as the company continuously works on improving its product.

One of the key use cases of CircleCI is running tests on every commit to GitHub and deploying to development and production environments based on the branch. This allows engineering teams to ensure that bug-free code is shipped and accelerate the development process by automating the building, testing, and deployment of non-production environments. CircleCI also supports the automation of various build and test processes, including running pre-deploy and post-deploy scripts, executing test suites, and sending notifications through platforms like Slack.

Another important use case of CircleCI is its ability to handle the build process for different types of applications, such as Android, iOS, and web applications. By outsourcing the management of build servers to CircleCI, teams can focus more on developing custom applications while relying on a robust continuous integration and delivery solution. Moreover, CircleCI's concurrency feature allows users to split out test suites across multiple slices, significantly improving efficiency and reducing testing time. Additionally, CircleCI has been widely adopted for its cloud integration capabilities, allowing users to run automated tests in parallel containers.

In conclusion, CircleCI is extensively used by engineering teams for continuous integration and deployment pipelines across various software applications and environments. It simplifies the deployment process for Drupal and WordPress websites to platforms like Pantheon and provides a customizable environment for building, testing, and deploying workflows. With its tight integration with GitHub, responsive support team, and reliable performance reported by users from different industries, CircleCI is a popular choice for automating and optimizing the development process.

Constant improvement: Users appreciate the continuous enhancements and additions made to CircleCI, demonstrating the company's commitment to providing a high-quality product. Many users have expressed their satisfaction with the constant improvement of CircleCI.

Responsive support: The highly responsive and helpful support provided by CircleCI is valued by users when they encounter any issues. Numerous users have praised the responsiveness and helpfulness of CircleCI's support team.

Seamless integration with GitHub: Users praise the seamless integration between CircleCI and GitHub, highlighting its reliability and efficiency in not missing any commits. Many reviewers have specifically mentioned the seamless integration between CircleCI and GitHub as one of its standout features.

  1. Lack of Communication about Updates: Some users have expressed frustration with the lack of communication regarding updates and breaking changes. They have reported that it takes too long for account representatives to respond to their questions, causing delays in their workflow.

  2. Confusing Configuration Options: Users have criticized the organization of options in the config file, finding it arbitrary and unhelpful for managing their configurations effectively. This confusion has led to difficulties in setting up and maintaining their projects on CircleCI.

  3. Limited Customization Options: Several users have mentioned that they find the customization options on CircleCI somewhat limited compared to other tools like Jenkins. They desire more flexibility and control over their build processes and workflows, which they feel is not fully provided by CircleCI's current feature set.

  • Many users recommend starting with the free trial of CircleCI to get a solid CI/CD experience. They suggest taking advantage of this opportunity to explore the platform's features and evaluate its suitability for their needs.

  • Several reviewers recommend leveraging the full power of CircleCI by using orbs and workflows. These features enable users to streamline their CI/CD processes and improve efficiency in managing complex workflows.

  • Users often recommend keeping configurations simple and making use of parallelization to optimize build times. By simplifying configurations and running tasks in parallel, teams can reduce build times and improve overall productivity in their CI/CD pipeline.

Attribute Ratings

Reviews

(1-15 of 15)
Companies can't remove reviews or game the system. Here's why
Score 8 out of 10
Vetted Review
Verified User
Incentivized
We use CircleCI for continuous integration and delivery of our mobile app. The main users are our DevOps team to help manage code releases. It's helped us push code to production with a standardize process and can now ensure we get a build with each merge. Our codebase is ReactNative and run on AWS CloudFront.
  • Automated builds and process
  • Simple too use and set up
  • Scales well as we integrated additional projects
  • Sometimes hard to debug issues with builds and unable to find help
  • Customizations not supported
  • Outages impacted our workflow
It's one of the stronger options when we considered CI/CD solutions. It's commonly used in the industry so when we have new team members join it's easy for them to pick up. Generally it's been reliable aside from a few outages. I would recommend this for any software teams that also run automated tests.
Sagiv Frankel | TrustRadius Reviewer
Score 8 out of 10
Vetted Review
Verified User
Incentivized
We use CircleCI for most of our development workflows. Building, testing and deploying. We use it across most teams and departments.
It integrated nicely with GitHub and we are able to validate every change on every branch before merging and automatically deploying to production. I use it for both Ruby and React projects.
  • Shows a clear workflow diagram and be able to re-run specific steps.
  • Fast set-up integration with GitHub.
  • Jobs can sometimes take too long.
  • Documentation on how to set up could be improved.
We have many developers that push to production every day. Every branch runs continuous integration on CircleCI and clearly links to GitHub with an indication on whether it failed or passed.
Things work fine when you work against the GitHub links but searching on the CircleCI site is not intuitive.
Configuration with YAML files can also be hard to do and some UI tools for scaffolding them would be nice.
Javier Cardoso | TrustRadius Reviewer
Score 8 out of 10
Vetted Review
Verified User
Incentivized
At the moment, Circle is used across the company to make continuous integration and continuous delivery for the mobile native applications. Circle went to solve us the problem of have a dynamic and easy-to-use cloud-based continuous integration and delivery for mobile, without the maintenance cost of the resources and using only for the computing use.
  • Jobs Configuration: I think that the configuration way of Circle CI is very simple and useful. You only have to add an YAML file in your Git repository root and add some tasks inside it.
  • Environment Variables Encryption: The way to encrypt sensible data, for example tokens or credentials, is very simple and secure.
  • The compute credit cost is cheap: You don't need a large amount of money to start using Circle.
  • Cost per user: The cost per user is very high.
  • UI: The UI is not as intuitive as I need. If you have a lot of applications enabled, it's a bit difficult to find in the home page the build which you're looking for.
  • The billing and usage information: It's a feature that was enabled in 2019 June. But it's not specific to any place, and the information of June is incomplete.
Circle suits if you're looking for a cloud-based continuous integration and continuous delivery system for web and native-based applications. The uptime is very good and the features included in the platform are very useful.
On the other hand, it's a little difficult to combine Circle with your on-premise stuff, such as registry dependencies (npm, Maven Nexus, etc) ... because the only way is to give Circle access to your on-premise network and it could be a little insecure.
Score 9 out of 10
Vetted Review
Verified User
Incentivized
CircleCI is being used as the main product for continuous integration, continuous delivery software development. It's being used primarily by release management/engineering and software engineering teams. It is solving the problem of needing to build a process around pushing code into production and following a schedule where code is continually deployed.
  • Continuous deployment
  • Continuous integration
  • Process building for engineering deployment
  • User interface and experience
  • Support for cloud provider integration directly
CircleCI is one of the best CI/CD pipeline tools available. I'm not sure I can advise anything else besides this because it's still the most used and continually developed tools.
Score 7 out of 10
Vetted Review
Verified User
Incentivized
We've used CircleCI for the automation of build and test for smaller scale projects, in combination with another set of tools for continual deployment, hosting and visual testing. CircleCI is a great interface for viewing and managing automated jobs and workflows, and has made the process of CI more accessible for the team as a whole.
  • Simple integration with the provided YAML template
  • Quick setup with Git repos
  • Easy to add new jobs
  • Quick integration with related visual testing tools
  • Limited options on free plan
  • Sometimes buggy when modifying jobs
  • Jump between new and old UI
Great for quick setup of new projects, but may not be the most suitable to large scale production apps (not from experience, but the level of detail may not be sufficient - at least on the free tier).
Score 9 out of 10
Vetted Review
Verified User
Incentivized
CircleCI is being used by my team as a continuous integration / continuous deployment pipeline for code and various other programmatic work. The business problems it addresses is the deployment, testing, and productionization of code supporting our main software engineering functions. Various other teams we work with also go along this pathway and use circle or other tools.
  • continuous integration
  • test driven development
  • continuous deployment
  • scope of view
  • better pricing model
  • better personalized support
CircleCI is great when you have software engineering processes that you need to take out and drastically scale and test before deployment. It works with regular code structures where there's a procedural lifecycle and where there is a need to methodically test and deploy code in an automated manner so deployments no longer need to be done by hand.
Dillon Welch | TrustRadius Reviewer
Score 8 out of 10
Vetted Review
Verified User
Incentivized
We use CircleCI to run our React tests as well as build and deploy our React code to AWS CloudFront on both staging and production.
  • Deploy to AWS
  • Integrate with GitHub
  • Ruby support
  • JavaScript support
  • YAML files require a lot of configuration for basic setup
  • Pricing outside of the free tier is pretty costly for what's offered
  • Hard to rebuild a single job in a workflow
  • Hard to setup a configuration with multiple dependencies (for example, both node and Python)
CircleCI is well suited for a small team that needs to run tests on web app codes like Ruby on Rails, React, Python, etc. It's not as well suited for larger teams as the cost quickly scales up. It's also not well suited for more complicated builds because the configuration process is pretty arcane.
December 10, 2018

CircleCI is awesome

Score 9 out of 10
Vetted Review
Verified User
Incentivized
We're using CircleCI to run continuous integration for both front-end and back-end components for a SaaS application. It's linked to a popular source code repository which makes integration quite easy.

Overall, the experience has been fantastic. We're a small firm, and no need for the paid plan yet. But have successfully used the tool to bootstrap for the time being. The communities are quite helpful, even for those who don't have a paid plan for premium support. Would heartily recommend to colleagues.
  • Git integration with popular providers. Github and Bitbucket for starters. Makes it super simple to get started.
  • Straightforward CI tooling. No need to spin up a CI server like Jenkins / TeamCity to get things moving.
  • Strong community forums. Ran into a bug once, and as I was on the free tier didn't have access to premium support. Was able to work out the issue via community support.
  • Bits of the caching configuration were initially a bit confusing.
  • Took a bit of time to get git submodules working properly. But that's to be expected as it's not a common denominator for most Git repositories.
  • Running local builds for diagnosing bugs can be a bit cumbersome. The docker image I recall was very much a black box, and was unclear how to interpret why I got the results I did. But again, expected. If it were not a black box, it would be trivial for other vendors to clone their functionality.
For basic CI/CD, CircleCI is the way to go. Especially for smaller projects where not a tremendous amount of complexity or build time is required.

Strongly recommend for simple projects. And will likely become a paying customer when the complexity/build time is merited.

Haven't come across scenarios where its not well suited. Perhaps for very large organizations who want full control over their CI/CD environments.
Paul Hepworth | TrustRadius Reviewer
Score 8 out of 10
Vetted Review
Verified User
Incentivized
We use CircleCi as an integral to our continuous delivery pipeline across engineering. Using Circle allows us to focus on our application development. The concurrency of builds helps us split out our test suite across 15 different slices. Tight integration with GitHub allows us to easily integrate into pull request checks. While there are occasional hiccups there are way fewer problems than any other CI tool we've used in the past and we've used several different ones. Support is also pretty responsive and it's apparent that Circle is continuing to improve their product.
  • Concurrency of builds (we use 15)
  • Constant improvement to service by adding features and optimizations
  • When things go wrong their support is responsive and helpful.
  • Proactive communication about updates and breaking changes
  • Questions to account rep can sometimes take too long (for us -- > 1 day) to respond
I wonder if we are growing out of Circle. Can we increase concurrency beyond 15? While circle is helpful when things go wrong we sometimes have problems for several days in a row (recently) and each time there is some different reason that sounds like a one-off. Makes me wonder if there is something more going on.
Score 10 out of 10
Vetted Review
Verified User
Incentivized
CircleCI is being used by our organization for continual integration and automated deployment of Drupal and WordPress websites to Pantheon, among many other smaller CI jobs. It is used entirely by our Development and DevOps team members. It allows us to commit a simple config file to Git that controls the way that our software gets deployed, making the tedious job of deploying changes for hundreds of websites regularly much simpler.
  • Full customization and scripting abilities. Using tools like bash scripts, SSH, and Node, running almost anything upon committing some code to GitHub becomes possible.
  • Integration with all of our favorite services. GitHub and Slack in particular are crucial to our business and CircleCI's integration is seamless and full-featured.
  • Great config file syntax. Many CI services require you to perform advanced configuration in a UI. This is fine at first (and CircleCI offers this for many options available), but when you start needing to manage a large number of projects, committing configuration changes to a Git repository is more consistent and maintainable than making the change many different times manually in a UI.
  • It would be nice if you could configure everything via the YML file. Some things are only available via YML, and some things are actually only available in the UI, and many other things have full overlap between the two. I'm sure there are good reasons for this, but this is a pretty confusing situation. For example, certain PHP versions are only available on certain Ubuntu releases. Configuring the PHP version is done via the .yml file, but configuring the Ubuntu release being used for the build has to be done in the UI. This can easily lead to things not building properly.
For relatively advanced users comfortable with YAML configuration and the GitHub workflow, I wholeheartedly recommend CircleCI and think it's perfectly suited. For people who prefer to work completely in a user interface and not edit text files, there are other solutions more suited to that scenario.
January 18, 2017

Testing FTW!

Jake Mercurio | TrustRadius Reviewer
Score 9 out of 10
Vetted Review
Verified User
Incentivized
We're using CircleCI to run our suite of unit tests for a few projects (we handle end-to-end testing separately). We love that it auto-runs tests on git commits, runs our tests in parallel containers, and is configured with a simple YAML file. The UX is super clean and easy to debug when things go wrong. We're part of their beta program and they have some great features coming down the product pipeline that addresses our few headaches like their lack of support for "docker exec" (you have to use lxc-attach) and old Ubuntu containers.

We use this product every day and we're pretty happy with it.
  • Parallel testing - run your unit tests in parallel containers shared across all branches.
  • UX - When your tests fail CircleCI makes it easy to see what failed and why.
  • Configuration - whether your project runs NodeJS, PHP, Docker, Java, or whatever else you can control just about every step of the provisioning process.
  • Price - You pay by concurrent containers. We're currently using 10 to run unit test across dozens of branches for a completely reasonable price. No caches.
  • Incomplete Docker support - currently CircleCi doesn't support docker exec (although they have a workaround), which is a little frustrating for our team.
  • Old Ubuntu versions - the containers used to use Ubuntu Precise which made provisioning more difficult, but they are currently moving to Trusty Tahr.
CircleCI is well suited to any project where you have:
  • A quick provisioning process or can use a pre-configured CircleCi container
  • Have lots of unit tests and only a few integration tests
  • Use standard testing libraries like PhpUnit, Mocha, Jasmine, JUnit, etc.
  • Have a small-medium budget
  • Your test suite takes more than 5 minutes to run
Dmitry Sadovnychyi | TrustRadius Reviewer
Score 9 out of 10
Vetted Review
Verified User
Incentivized
[It is being used for] running the test suite on each commit and deploying different versions.
  • Really easy to set it up, supports most of the languages out of the box
  • Free to use with some limitations
  • Easier key management
If you use popular languages and frameworks you definitely should give it a try – it's very easy to set it up.
Micah Hausler | TrustRadius Reviewer
Score 10 out of 10
Vetted Review
Verified User
Incentivized
We initially implemented it for automated testing of all our private repositories, and have been overall very happy with it. We looked at using it for our open source projects, but due to the fact that it doesn't support build matrices, we ended up going with Travis CI for public projects.
  • It is very easy to set up, you can even set it up without a configuration file and it will try to infer your test runner and language.
  • It is easy to configure with a straight-forward YAML configuration.
  • It has great integration with services like Github and Slack.
  • You can easily debug broken builds by SSH-ing into the test container and quickly figure out what is going wrong.
  • There is no configuration difference for public or private repositories, CircleCi appropriately mirrors Github.
  • The pricing allows for unlimited repositories, the tiers are based on parallel builds. This is great if you have a lot of private repos.
  • I really wish CircleCI had the ability to have a build matrix (like Travis CI), for example, run my python tests against all four combinations of Python 2 and 3, and say Django 1.8 and 1.9.
  • Support is generally pretty good, but can be hit or miss on timing. I've had quick responses, and other times waited multiple days for a response.
Again, it's very well suited for teams with many private repositories, and that want to have simple configuration across projects.
January 12, 2017

Fast and Easy CI

Austin Riendeau | TrustRadius Reviewer
Score 9 out of 10
Vetted Review
Verified User
Incentivized
I use Circle CI for continuous integration and delivery. It runs all of the tests and builds before our code ever sees production. It also notifies GitHub before we merge the code. I also utilize the use of Docker which Circle CI supports fully and makes running clean builds easier.
  • Clean user experience
  • Docker support
  • Fast and easy
  • Clean documentation
  • Faster builds
  • Non-GitHub support
I have yet to find a good example of when not to use Circle CI unless you are building mobile applications. It is not best suited for that at this time. I think TravisCI is the best currently for iOS builds. I use it currently for Go and Node applications.
Ken Yee | TrustRadius Reviewer
Score 8 out of 10
Vetted Review
Verified User
Incentivized
CircleCI was used to handle the build process for Raizlabs' Android, iOS, and web applications. It was used by the entire organization except for Xamarin apps which we built on our internal build server using Mac Minis that were unfortunately also used for videoconferencing. Using CircleCI let us outsource the management of the build servers so we didn't have to worry about them running out of space or slowing down videoconferencing.
  • CircleCI let us use someone else's infrastructure.
  • The circle.yml file for configuring a build was liked a lot more by our users because it was easy to use.
  • CircleCI is one of the few companies that can do iOS builds.
  • CircleCI does not support Xamarin builds...that prevented us from moving all our build infrastructure to CircleCI.
  • CircleCI's Android containers didn't always have the most updated SDKs so we frequently had to include updating SDKs as part o the build process.
CircleCI is best suited for smaller companies that don't have time to manage their build infrastructure and their entire source repository is also on a third party provider such as github or bitbucket. For larger companies who want to have more control over their build servers, it may not be as appropriate.
Return to navigation